RTP Profile for Audio and Video Conferences with Minimal Control

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as ''work in progress''. To learn the current status of any Internet-Draft, please check the ''1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), ABSTRACT This memo describes a profile called ''RTP/AVP'' for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings. The document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names when used within RTP. However, the encoding definitions are independent of the particular transport mechanism used. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications. Changes This draft revises RFC 1890. It is fully backwards-compatible with RFC 1890 and codifies existing practice. It is intended that this draft form the basis of a new RFC to obsolete RFC 1890 as it moves to Draft Standard. Besides wording clarifications and filling in RFC numbers for payload type definitions, this draft adds payload types 4, 16, 17, 18, 19 and 34. The PostScript version of this draft contains change bars marking changes make since draft-00. A tentative TCP encapsulation is defined. Note to RFC editor: This section is to be removed before publication as an RFC. All RFC TBD should be filled in with the number of the RTP specification RFC submitted for Draft Standard status.